Antifraud Resilient Transaction Identifier Datastructure Apparatuses, Methods and Systems

ABSTRACT

The Antifraud Resilient Transaction Identifier Datastructure Apparatuses, Methods and Systems (“ARTID”) transforms PIN, unique user identifying device datastructure inputs via ARTID components into secure payment authorization outputs. The ARTID includes a virtual secure element datastructure transaction apparatus, comprising, a memory, a component collection in the memory, and a processor disposed in communication with the memory, and configured to issue a plurality of processing instructions from the component collection stored in the memory. ARTID includes instructions to: obtain request to generate a tamper resistant asset account from a requestor, and instantiate a new tamper resistant asset account, wherein the account is populated with the requestor identifier, unique requestor device identifier, a secure cryptographic element for the tamper resistant account. ARTID also includes instructions to provide a message to generate a new physical account card and an associated virtual account card associated with the tamper resistant asset account, and obtain a request to engage the virtual account card in a transaction, wherein the request includes the user access credential. ARTID also includes instructions to generate a card access event message from the request to engage the virtual account card, provide the card access event message to a payment network, and obtain a card access event authorization response.

PRIORITY CLAIM

Applicant hereby claims benefit to priority under 35 USC § 119 as anon-provisional conversion of U.S. provisional patent application Ser.No. 62/660,841, filed Apr. 20, 2018, entitled “Antifraud ResilientTransaction Identifier Datastructure Apparatuses, Methods and Systems”,(attorney docket no. Muxi0002PV).

Applicant also hereby claims benefit to priority under 35 USC § 120 as acontinuation-in-part of U.S. patent application Ser. No. 15/178,532,filed Jun. 9, 2016, entitled “Point of Sale Apparatuses, Methods andSystems”, (attorney docket no. MUXI0001US); and which in turn claimsbenefit to priority under 35 USC § 119 as a non-provisional conversionsof: U.S. provisional patent application Ser. No. 62/174,449, filed Jun.11, 2015, entitled “Virtualized Point of Sale Terminal Apparatuses,Methods and Systems,” (attorney docket no. Muxi0001PV); and U.S.provisional patent application Ser. No. 62/249,919, filed Nov. 2, 2015,entitled “Virtualized Point of Sale Terminal Apparatuses, Methods andSystems,” (attorney docket no. MUXI0001PV2).

The entire contents of the aforementioned applications are hereinexpressly incorporated by reference.

This application for letters patent disclosure document describesinventive aspects that include various novel innovations (hereinafter“disclosure”) and contains material that is subject to copyright, maskwork, and/or other intellectual property protection. The respectiveowners of such intellectual property have no objection to the facsimilereproduction of the disclosure by anyone as it appears in publishedPatent Office file/records, but otherwise reserve all rights.

FIELD

The present innovations generally address data security, and moreparticularly, include Antifraud Resilient Transaction IdentifierDatastructure Apparatuses, Methods and Systems.

However, in order to develop a reader's understanding of theinnovations, disclosures have been compiled into a single description toillustrate and clarify how aspects of these innovations operateindependently, interoperate as between individual innovations, and/orcooperate collectively. The application goes on to further describe theinterrelations and synergies as between the various innovations; all ofwhich is to further compliance with 35 U.S.C. § 112.

BACKGROUND

Data security systems often use a Personal Identification Number (PIN)to secure data. Various credit card systems include Credit CardIdentification Number (CCID) numbers to protect from unauthorized accessto credit card accounts. Newer credit cards combine chip and PIN to helpprevent unauthorized access to credit cards.

BRIEF DESCRIPTION OF THE DRAWINGS

Appendices and/or drawings illustrating various, non-limiting, example,innovative aspects of the Antifraud Resilient Transaction IdentifierDatastructure Apparatuses, Methods and Systems (hereinafter “ARTID”)disclosure, include:

FIG. 1 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 2 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 3 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 4 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 5 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 6 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 7 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 8 shows a datagraph illustrating data flow(s) for the ARTID;

FIG. 9 shows a data structure for the ARTID;

FIG. 10 shows a data structure for the ARTID;

FIG. 11 shows a data structure for the ARTID.

FIG. 12 shows a block diagram illustrating embodiments of a ARTIDcontroller;

APPENDIX 1 illustrate embodiments of the ARTID.

Generally, the leading number of each citation number within thedrawings indicates the figure in which that citation number isintroduced and/or detailed. As such, a detailed discussion of citationnumber 101 would be found and/or introduced in FIG. 1. Citation number201 is introduced in FIG. 2, etc. Any citations and/or reference numbersare not necessarily sequences but rather just example orders that may berearranged and other orders are contemplated. Citation number suffixesmay indicate that an earlier introduced item has been re-referenced inthe context of a later figure and may indicate the same item,evolved/modified version of the earlier introduced item, etc., e.g.,server 199 of FIG. 1 may be a similar server 299 of FIG. 2 in the sameand/or new context.

DETAILED DESCRIPTION

The Antifraud Resilient Transaction Identifier DatastructureApparatuses, Methods and Systems (hereinafter “ARTID”) transforms PIN,unique user identifying device datastructure inputs, via ARTIDcomponents (e.g., EMV APDU, etc. components), into secure paymentauthorization outputs. The ARTID components, in various embodiments,implement advantageous features as set forth below.

Introduction

The ARTID provides unconventional features (e.g., a virtual secureelement datastructure transaction apparatus having a: request togenerate a tamper resistant asset account from a requestor,instantiation of a new tamper resistant asset account, generation of anaccount card associated with the tamper resistant asset account,generation of a card access event message from the request to engage theaccount card) that were never before available in data security.

In one embodiment, the ARTID places card encrypted data having a secureelement into a certified hardware security module (HSM). In oneembodiment, the ARTID clones a physical card infrastructure (e.g.,including a PIN pad and Europay, Mastercard and Visa (EMV) card, etc.)into a network accessible infrastructure. The HSM is configured toemulate a chip and pin pad and have access to a virtual card that is thesame as a physical credit card. The HSM houses this emulated secureelement and pin pad and is disposed in communication with, an acquirerterminal, a payment network, an issuer. The ARTID provides a PIN, uniqueuser identifying device datastructure it generates from a combination ofuser data and user device unique identifying information such as (UUID,etc.).

ARTID Example Datastructure Commands

The ARTID may include various datastructures:

Get card request format:

Position Format Description 001-002 N2 Identifier of the AcquiringNetwork, according to the Parameter x AID Table. To cover all networks,you must use the value “00”. 003-004 N2 Type of application desired,according to Parameter x AID Table. For any application, use “99”. For alist of specific applications, use “00”. 005-016 N12 Initial transactionvalue in cents (Amount, authorized), can be 0 (zero) if this data is notavailable at the beginning of the transaction. 017-022 N6 Date oftransaction (“AAMMDD”) 023-028 N6 Transaction Time (“HHMMSS”) 029-038N10 “Time-stamp”of the parameter tables, formed by day, month, year anda sequential number (“DDMMAAAASS”) - see Chapter 4. If an AcquirerNetwork is defined, this “time-stamp” refers only to the tables relatedto it. 039-040 N2 Number of entries in the following list, if desiredapplication type is “00” IMPORTANT: This field is not optional, andshould receive the value “00” if there is no list below. 041-??? N4Network identifier + index for Parameter x AID Table. . . . . . .???-??? N4 Network identifier + index for Parameter x AID Table. ???-???N3 Size in bytes of the following tag list (“000” to “yyy”). ???-???Hxxx(Byyy) List of tags (**) for field 55 of the ISO8583 message field.

Get card response format:

Position Format Description 001-002 N2 Type of card read: “00” -Magnetic, “01” - VISA Cash Coin Makers on TIBC v1, “02” - VISA Cash CoinMakers on TIBC v3, “03” - EMV with contact, “04” - Easy-Entry on TIBCv1, “05” - Contactless chip simulating stripe, “06” - Non-contact EMV003 N1 Status of last chip card reading. “0” - Successful (or otherstatus that does not involve fallback). In this case the magnetic cardwith indication of the presence of chip should not be accepted. “2” -Required application not supported. 004-005 N2 Type of applicationselected, according to Parameter x AID Table (position 043-044). 006-007N2 Identifier of the acquiring network, according to Parameter x AIDTable (position 005-006). 008-009 N2 Register Index of Parameter x AIDTable (position 007-008). 010-011 N2 Track 1 Size 012-087 A76 Track 1(without sentries and formatting byte - first alphanumeric character),left-aligned with spaces to the right 088-089 N2 Track 2 Size 090-126A37 Track 2 (without sentries), left-aligned with spaces to the right127-129 N3 Track size 3 130-233 A104 Track 3 (without sentries),left-aligned with spaces to the right 234-235 N2 PAN size 236-254 A19PAN, left-aligned with spaces to the right 255-256 N2 Application PANSequence Number 257-272 A16 Application Label, with spaces to the right.273-275 N3 Service Code 276-301 A26 Cardholder Name, with spaces to theright 302-307 N6 Application Expiration Date (YYMMDD) 308-309 N2 Size ofthe card's external number. 310-328 A19 External number of the card,left-aligned with spaces to the right 329-336 N8 Balance, for coin case.337-339 N3 Issuer Country Code 340-342 N3 The following data size, incharacters 343-??? A??? List of tags for field 55 of the ISO8583 messagefield.

Encrypt data request format:

Position Format Description 001 N1 Encryption Mode: “0” - MasterKey/Working DES (8 bytes) “1” - Master Key/Working 3DES (16 bytes) “2” -DUKPT DES “3” - DUKPT Triple-DES 002-003 N2 Master Key Index or DUKPTTreatment Record 004-035 H32(B16) Working Key (encrypted by Master Key),and in “0” mode, only the first 8 bytes are used. Data to be encrypted.036-037 N2 Clear data size, in bytes 038-??? Hxx(Byy) Clear data.

Encrypt data response format, DUKPT case:

Position Format Description Position Format Description 001-020 H20(B10) Serial Number of Key (Key Serial Number) and Counter (KeyCounter). 021-022 N2 Encrypted data size, in bytes (equal to input size)023-??? Hxx(Byy) Encrypted data.

Encrypt data response format, master key case

Position Format Description 001-002 N2 Encrypted data size, in bytes(equal to input size) 003-??? Hxx(Byy) Encrypted data.

FIG. 1 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 2 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 3 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 4 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 5 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 6 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 7 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 8 shows a datagraph illustrating data flow(s) for the ARTID.

FIG. 9 shows a data structure for the ARTID.

FIG. 10 shows a data structure for the ARTID.

FIG. 11 shows a data structure for the ARTID.

ARTID Controller

FIG. 12 shows a block diagram illustrating embodiments of a ARTIDcontroller. In this embodiment, the ARTID controller 1201 may serve toaggregate, process, store, search, serve, identify, instruct, generate,match, and/or facilitate interactions with a computer through datasecurity technologies, and/or other related data.

Users, which may be people and/or other systems, may engage informationtechnology systems (e.g., computers) to facilitate informationprocessing. In turn, computers employ processors to process information;such processors 1203 may be referred to as central processing units(CPU). One form of processor is referred to as a microprocessor. CPUsuse communicative circuits to pass binary encoded signals acting asinstructions to allow various operations. These instructions may beoperational and/or data instructions containing and/or referencing otherinstructions and data in various processor accessible and operable areasof memory 1229 (e.g., registers, cache memory, random access memory,etc.). Such communicative instructions may be stored and/or transmittedin batches (e.g., batches of instructions) as programs and/or datacomponents to facilitate desired operations. These stored instructioncodes, e.g., programs, may engage the CPU circuit components and othermotherboard and/or system components to perform desired operations. Onetype of program is a computer operating system, which, may be executedby CPU on a computer; the operating system enables and facilitates usersto access and operate computer information technology and resources.Some resources that may be employed in information technology systemsinclude: input and output mechanisms through which data may pass intoand out of a computer; memory storage into which data may be saved; andprocessors by which information may be processed. These informationtechnology systems may be used to collect data for later retrieval,analysis, and manipulation, which may be facilitated through a databaseprogram. These information technology systems provide interfaces thatallow users to access and operate various system components.

In one embodiment, the ARTID controller 1201 may be connected to and/orcommunicate with entities such as, but not limited to: one or more usersfrom peripheral devices 1212 (e.g., user input devices 1211); anoptional cryptographic processor device 1228; and/or a communicationsnetwork 1213.

Networks comprise the interconnection and interoperation of clients,servers, and intermediary nodes in a graph topology. It should be notedthat the term “server” as used throughout this application refersgenerally to a computer, other device, program, or combination thereofthat processes and responds to the requests of remote users across acommunications network. Servers serve their information to requesting“clients.” The term “client” as used herein refers generally to acomputer, program, other device, user and/or combination thereof that iscapable of processing and making requests and obtaining and processingany responses from servers across a communications network. A computer,other device, program, or combination thereof that facilitates,processes information and requests, and/or furthers the passage ofinformation from a source user to a destination user is referred to as a“node.” Networks are generally thought to facilitate the transfer ofinformation from source points to destinations. A node specificallytasked with furthering the passage of information from a source to adestination is called a “router.” There are many forms of networks suchas Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs),Wireless Networks (WLANs), etc. For example, the Internet is, generally,an interconnection of a multitude of networks whereby remote clients andservers may access and interoperate with one another.

The ARTID controller 1201 may be based on computer systems that maycomprise, but are not limited to, components such as: a computersystemization 1202 connected to memory 1229.

Computer Systemization

A computer systemization 1202 may comprise a clock 1230, centralprocessing unit (“CPU(s)” and/or “processor(s)” (these terms are usedinterchangeable throughout the disclosure unless noted to the contrary))1203, a memory 1229 (e.g., a read only memory (ROM) 1206, a randomaccess memory (RAM) 1205, etc.), and/or an interface bus 1207, and mostfrequently, although not necessarily, are all interconnected and/orcommunicating through a system bus 1204 on one or more (mother)board(s)1202 having conductive and/or otherwise transportive circuit pathwaysthrough which instructions (e.g., binary encoded signals) may travel toeffectuate communications, operations, storage, etc. The computersystemization may be connected to a power source 1286; e.g., optionallythe power source may be internal. Optionally, a cryptographic processor1226 may be connected to the system bus. In another embodiment, thecryptographic processor, transceivers (e.g., ICs) 1274, and/or sensorarray (e.g., accelerometer, altimeter, ambient light, barometer, globalpositioning system (GPS) (thereby allowing ARTID controller to determineits location), gyroscope, magnetometer, pedometer, proximity,ultra-violet sensor, etc.) 1273 may be connected as either internaland/or external peripheral devices 1212 via the interface bus I/O 1208(not pictured) and/or directly via the interface bus 1207. In turn, thetransceivers may be connected to antenna(s) 1275, thereby effectuatingwireless transmission and reception of various communication and/orsensor protocols; for example the antenna(s) may connect to varioustransceiver chipsets (depending on deployment needs), including:Broadcom® BCM4329FKUBG transceiver chip (e.g., providing 802.11n,Bluetooth 2.1+EDR, FM, etc.); a Broadcom® BCM4752 GPS receiver withaccelerometer, altimeter, GPS, gyroscope, magnetometer; a Broadcom®BCM4335 transceiver chip (e.g., providing 2G, 3G, and 4G long-termevolution (LTE) cellular communications; 802.11ac, Bluetooth 4.0 lowenergy (LE) (e.g., beacon features)); a Broadcom® BCM43341 transceiverchip (e.g., providing 2G, 3G and 4G LTE cellular communications; 802.11g/, Bluetooth 4.0, near field communication (NFC), FM radio); anInfineon Technologies® X-Gold 618-PMB9800 transceiver chip (e.g.,providing 2G/3G HSDPA/HSUPA communications); a MediaTek® MT6620transceiver chip (e.g., providing 802.11a/ac/b/g/n, Bluetooth 4.0 LE,FM, GPS; a Lapis Semiconductor® ML8511 UV sensor; a maxim integratedMAX44000 ambient light and infrared proximity sensor; a TexasInstruments® WiLink WL1283 transceiver chip (e.g., providing 802.11n,Bluetooth 3.0, FM, GPS); and/or the like. The system clock may have acrystal oscillator and generates a base signal through the computersystemization's circuit pathways. The clock may be coupled to the systembus and various clock multipliers that will increase or decrease thebase operating frequency for other components interconnected in thecomputer systemization. The clock and various components in a computersystemization drive signals embodying information throughout the system.Such transmission and reception of instructions embodying informationthroughout a computer systemization may be referred to ascommunications. These communicative instructions may further betransmitted, received, and the cause of return and/or replycommunications beyond the instant computer systemization to:communications networks, input devices, other computer systemizations,peripheral devices, and/or the like. It should be understood that inalternative embodiments, any of the above components may be connecteddirectly to one another, connected to the CPU, and/or organized innumerous variations employed as exemplified by various computer systems.

The CPU comprises at least one high-speed data processor adequate toexecute program components for executing user and/or system-generatedrequests. The CPU is often packaged in a number of formats varying fromlarge supercomputer(s) and mainframe(s) computers, down to minicomputers, servers, desktop computers, laptops, thin clients (e.g.,Chromebooks®), netbooks, tablets (e.g., Android®, iPads®, and Windows®tablets, etc.), mobile smartphones (e.g., Android®, iPhones®, Nokia®,Palm® and Windows® phones, etc.), wearable device(s) (e.g., watches,glasses, goggles (e.g., Google Glass), etc.), and/or the like. Often,the processors themselves will incorporate various specializedprocessing units, such as, but not limited to: integrated system (bus)controllers, memory management control units, floating point units, andeven specialized processing sub-units like graphics processing units,digital signal processing units, and/or the like. Additionally,processors may include internal fast access addressable memory, and becapable of mapping and addressing memory 1229 beyond the processoritself; internal memory may include, but is not limited to: fastregisters, various levels of cache memory (e.g., level 1, 2, 3, etc.),RAM, etc. The processor may access this memory through the use of amemory address space that is accessible via instruction address, whichthe processor can construct and decode allowing it to access a circuitpath to a specific memory address space having a memory state. The CPUmay be a microprocessor such as: AMD's Athlon®, Duron® and/or Opteron®;Apple's® A series of processors (e.g., A5, A6, A7, A8, etc.); ARM's®application, embedded and secure processors; IBM® and/or Motorola'sDragonBall® and PowerPC®; IBM's® and Sony's® Cell processor; Intel's®80X86 series (e.g., 80386, 80486), Pentium®, Celeron®, Core (2) Duo®, iseries (e.g., i3, i5, i7, etc.), Itanium®, Xeon®, and/or XScale®;Motorola's® 680X0 series (e.g., 68020, 68030, 68040, etc.); and/or thelike processor(s). The CPU interacts with memory through instructionpassing through conductive and/or transportive conduits (e.g., (printed)electronic and/or optic circuits) to execute stored instructions (i.e.,program code) according to various data processing techniques. Suchinstruction passing facilitates communication within the ARTIDcontroller and beyond through various interfaces. Should processingrequirements dictate a greater amount speed and/or capacity, distributedprocessors (e.g., see Distributed ARTID below), mainframe, multi-core,parallel, and/or super-computer architectures may similarly be employed.Alternatively, should deployment requirements dictate greaterportability, smaller mobile devices (e.g., Personal Digital Assistants(PDAs)) may be employed.

Depending on the particular implementation, features of the ARTID may beachieved by implementing a microcontroller such as CAST's® R8051XC2microcontroller; Intel's® MCS 51 (i.e., 8051 microcontroller); and/orthe like. Also, to implement certain features of the ARTID, some featureimplementations may rely on embedded components, such as:Application-Specific Integrated Circuit (“ASIC”), Digital SignalProcessing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or thelike embedded technology. For example, any of the ARTID componentcollection (distributed or otherwise) and/or features may be implementedvia the microprocessor and/or via embedded components; e.g., via ASIC,coprocessor, DSP, FPGA, and/or the like. Alternately, someimplementations of the ARTID may be implemented with embedded componentsthat are configured and used to achieve a variety of features or signalprocessing.

Depending on the particular implementation, the embedded components mayinclude software solutions, hardware solutions, and/or some combinationof both hardware/software solutions. For example, ARTID featuresdiscussed herein may be achieved through implementing FPGAs, which are asemiconductor devices containing programmable logic components called“logic blocks”, and programmable interconnects, such as the highperformance FPGA Virtex® series and/or the low cost Spartan® seriesmanufactured by Xilinx®. Logic blocks and interconnects can beprogrammed by the customer or designer, after the FPGA is manufactured,to implement any of the ARTID features. A hierarchy of programmableinterconnects allow logic blocks to be interconnected as needed by theARTID system designer/administrator, somewhat like a one-chipprogrammable breadboard. An FPGA's logic blocks can be programmed toperform the operation of basic logic gates such as AND, and XOR, or morecomplex combinational operators such as decoders or mathematicaloperations. In most FPGAs, the logic blocks also include memoryelements, which may be circuit flip-flops or more complete blocks ofmemory. In some circumstances, the ARTID may be developed on FPGAs andthen migrated into a fixed version that more resembles ASICimplementations. Alternate or coordinating implementations may migrateARTID controller features to a final ASIC instead of or in addition toFPGAs. Depending on the implementation all of the aforementionedembedded components and microprocessors may be considered the “CPU”and/or “processor” for the ARTID.

Power Source

The power source 1286 may be of any various form for powering smallelectronic circuit board devices such as the following power cells:alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium,solar cells, and/or the like. Other types of AC or DC power sources maybe used as well. In the case of solar cells, in one embodiment, the caseprovides an aperture through which the solar cell may capture photonicenergy. The power cell 1286 is connected to at least one of theinterconnected subsequent components of the ARTID thereby providing anelectric current to all subsequent components. In one example, the powersource 1286 is connected to the system bus component 1204. In analternative embodiment, an outside power source 1286 is provided througha connection across the I/O 1208 interface. For example, a USB and/orIEEE 1394 connection carries both data and power across the connectionand is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 1207 may accept, connect, and/or communicate to anumber of interface adapters, variously although not necessarily in theform of adapter cards, such as but not limited to: input outputinterfaces (I/O) 1208, storage interfaces 1209, network interfaces 1210,and/or the like. Optionally, cryptographic processor interfaces 1227similarly may be connected to the interface bus. The interface busprovides for the communications of interface adapters with one anotheras well as with other components of the computer systemization.Interface adapters are adapted for a compatible interface bus. Interfaceadapters variously connect to the interface bus via a slot architecture.Various slot architectures may be employed, such as, but not limited to:Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry StandardArchitecture ((E)ISA), Micro Channel Architecture (MCA), NuBus,Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express,Personal Computer Memory Card International Association (PCMCIA), and/orthe like.

Storage interfaces 1209 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices1214, removable disc devices, and/or the like. Storage interfaces mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),Institute of Electrical and Electronics Engineers (IEEE) 1394, fiberchannel, Small Computer Systems Interface (SCSI), Universal Serial Bus(USB), and/or the like.

Network interfaces 1210 may accept, communicate, and/or connect to acommunications network 1213. Through a communications network 1213, theARTID controller is accessible through remote clients 1233 b (e.g.,computers with web browsers) by users 1233 a. Network interfaces mayemploy connection protocols such as, but not limited to: direct connect,Ethernet (thick, thin, twisted pair 10/100/1000/10000 Base T, and/or thelike), Token Ring, wireless connection such as IEEE 802.11a-x, and/orthe like. Should processing requirements dictate a greater amount speedand/or capacity, distributed network controllers (e.g., see DistributedARTID below), architectures may similarly be employed to pool, loadbalance, and/or otherwise decrease/increase the communicative bandwidthrequired by the ARTID controller. A communications network may be anyone and/or the combination of the following: a direct interconnection;the Internet; Interplanetary Internet (e.g., Coherent File DistributionProtocol (CFDP), Space Communications Protocol Specifications (SCPS),etc.); a Local Area Network (LAN); a Metropolitan Area Network (MAN); anOperating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a cellular, WiFi,Wireless Application Protocol (WAP), I-mode, and/or the like); and/orthe like. A network interface may be regarded as a specialized form ofan input output interface. Further, multiple network interfaces 1210 maybe used to engage with various communications network types 1213. Forexample, multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 1208 may accept, communicate, and/orconnect to user, peripheral devices 1212 (e.g., input devices 1211),cryptographic processor devices 1228, and/or the like. I/O may employconnection protocols such as, but not limited to: audio: analog,digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus(ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared;joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; touchinterfaces: capacitive, optical, resistive, etc. displays; videointerface: Apple Desktop Connector (ADC), BNC, coaxial, component,composite, digital, Digital Visual Interface (DVI), (mini) displayport,high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video,VGA, and/or the like; wireless transceivers: 802.11a/ac/b/g/n/x;Bluetooth; cellular (e.g., code division multiple access (CDMA), highspeed packet access (HSPA(+)), high-speed downlink packet access(HSDPA), global system for mobile communications (GSM), long termevolution (LTE), WiMax, etc.); and/or the like. One output device mayinclude a video display, which may comprise a Cathode Ray Tube (CRT) orLiquid Crystal Display (LCD) based monitor with an interface (e.g., DVIcircuitry and cable) that accepts signals from a video interface, may beused. The video interface composites information generated by a computersystemization and generates video signals based on the compositedinformation in a video memory frame. Another output device is atelevision set, which accepts signals from a video interface. The videointerface provides the composited video information through a videoconnection interface that accepts a video display interface (e.g., anRCA composite video connector accepting an RCA composite video cable; aDVI connector accepting a DVI display cable, etc.).

Peripheral devices 1212 may be connected and/or communicate to I/Oand/or other facilities of the like such as network interfaces, storageinterfaces, directly to the interface bus, system bus, the CPU, and/orthe like. Peripheral devices may be external, internal and/or part ofthe ARTID controller. Peripheral devices may include: antenna, audiodevices (e.g., line-in, line-out, microphone input, speakers, etc.),cameras (e.g., gesture (e.g., Microsoft Kinect) detection, motiondetection, still, video, webcam, etc.), dongles (e.g., for copyprotection, ensuring secure transactions with a digital signature,and/or the like), external processors (for added capabilities; e.g.,crypto devices 528), force-feedback devices (e.g., vibrating motors),infrared (IR) transceiver, network interfaces, printers, scanners,sensors/sensor arrays and peripheral extensions (e.g., ambient light,GPS, gyroscopes, proximity, temperature, etc.), storage devices,transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles,monitors, etc.), video sources, visors, and/or the like. Peripheraldevices often include types of input devices (e.g., cameras).

User input devices 1211 often are a type of peripheral device 512 (seeabove) and may include: card readers, dongles, finger print readers,gloves, graphics tablets, joysticks, keyboards, microphones, mouse(mice), remote controls, security/biometric devices (e.g., fingerprintreader, iris reader, retina reader, etc.), touch screens (e.g.,capacitive, resistive, etc.), trackballs, trackpads, styluses, and/orthe like.

It should be noted that although user input devices and peripheraldevices may be employed, the ARTID controller may be embodied as anembedded, dedicated, and/or monitor-less (i.e., headless) device,wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers,processors 1226, interfaces 1227, and/or devices 1228 may be attached,and/or communicate with the ARTID controller. A MC68HC16microcontroller, manufactured by Motorola, Inc.®, may be used for and/orwithin cryptographic units. The MC68HC16 microcontroller utilizes a16-bit multiply-and-accumulate instruction in the 16 MHz configurationand requires less than one second to perform a 512-bit RSA private keyoperation. Cryptographic units support the authentication ofcommunications from interacting agents, as well as allowing foranonymous transactions. Cryptographic units may also be configured aspart of the CPU. Equivalent microcontrollers and/or processors may alsobe used. Other specialized cryptographic processors include: Broadcom's®CryptoNetX and other Security Processors; nCipher's® nShield; SafeNef s®Luna PCI (e.g., 7100) series; Semaphore Communications'® 40 MHzRoadrunner 184; Sun's® Cryptographic Accelerators (e.g., Accelerator6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano® Processor(e.g., L2100, L2200, U2400) line, which is capable of performing500+MB/s of cryptographic instructions; VLSI Technology's® 33 MHz 6868;and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor toaffect the storage and/or retrieval of information is regarded as memory1229. However, memory is a fungible technology and resource, thus, anynumber of memory embodiments may be employed in lieu of or in concertwith one another. It is to be understood that the ARTID controllerand/or a computer systemization may employ various forms of memory 1229.For example, a computer systemization may be configured wherein theoperation of on-chip CPU memory (e.g., registers), RAM, ROM, and anyother storage devices are provided by a paper punch tape or paper punchcard mechanism; however, such an embodiment would result in an extremelyslow rate of operation. In one configuration, memory 1229 will includeROM 1206, RAM 1205, and a storage device 1214. A storage device 1214 maybe any various computer system storage. Storage devices may include: anarray of devices (e.g., Redundant Array of Independent Disks (RAID)); adrum; a (fixed and/or removable) magnetic disk drive; a magneto-opticaldrive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable(R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); RAM drives; solidstate memory devices (USB memory, solid state drives (SSD), etc.); otherprocessor-readable storage mediums; and/or other devices of the like.Thus, a computer systemization generally requires and makes use ofmemory.

Component Collection

The memory 1229 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 1215 (operating system); information server component(s)1216 (information server); user interface component(s) 1217 (userinterface); Web browser component(s) 1218 (Web browser); database(s)1219; mail server component(s) 1221; mail client component(s) 1222;cryptographic server component(s) 1220 (cryptographic server); the ARTIDcomponent(s) 1235; and/or the like (i.e., collectively a componentcollection). These components may be stored and accessed from thestorage devices and/or from storage devices accessible through aninterface bus. Although unconventional program components such as thosein the component collection may be stored in a local storage device1214, they may also be loaded and/or stored in memory such as:peripheral devices, RAM, remote storage facilities through acommunications network, ROM, various forms of memory, and/or the like.

Operating System

The operating system component 1215 is an executable program componentfacilitating the operation of the ARTID controller. The operating systemmay facilitate access of I/O, network interfaces, peripheral devices,storage devices, and/or the like. The operating system may be a highlyfault tolerant, scalable, and secure system such as: Apple's MacintoshOS X (Server) and macOS®; AT&T Plan 9®; Be OS®; Blackberry's QNX®;Google's Chrome®; Microsoft's Windows® 7/8/10; Unix and Unix-like systemdistributions (such as AT&T's UNIX®; Berkley Software Distribution(BSD)® variations such as FreeBSD®, NetBSD, OpenBSD, and/or the like;Linux distributions such as Red Hat, Ubuntu, and/or the like); and/orthe like operating systems. However, more limited and/or less secureoperating systems also may be employed such as Apple Macintosh OS®(i.e., versions 1-9), IBM OS/2®, Microsoft DOS®, Microsoft Windows2000/2003/3.1/95/98/CE/Millenium/Mobile/NT/Vista/XP (Server)®, Palm OS®,and/or the like. Additionally, for robust mobile deploymentapplications, mobile operating systems may be used, such as: Apple'siOS®; China Operating System COS®; Google's Android®; Microsoft WindowsRT/Phone®; Palm's WebOS®; Samsung/Intel's Tizen®; and/or the like. Anoperating system may communicate to and/or with other components in acomponent collection, including itself, and/or the like. Mostfrequently, the operating system communicates with other programcomponents, user interfaces, and/or the like. For example, the operatingsystem may contain, communicate, generate, obtain, and/or provideprogram component, system, user, and/or data communications, requests,and/or responses. The operating system, once executed by the CPU, mayenable the interaction with communications networks, data, I/O,peripheral devices, program components, memory, user input devices,and/or the like. The operating system may provide communicationsprotocols that allow the ARTID controller to communicate with otherentities through a communications network 1213. Various communicationprotocols may be used by the ARTID controller as a subcarrier transportmechanism for interaction, such as, but not limited to: multicast,TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 1216 is a stored program component thatis executed by a CPU. The information server may be a an Internetinformation server such as, but not limited to Apache SoftwareFoundation's Apache, Microsoft's Internet Information Server, and/or thelike. The information server may allow for the execution of programcomponents through facilities such as Active Server Page (ASP), ActiveX,(ANSI) (Objective-) C (++), C # and/or .NET, Common Gateway Interface(CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH,Java, JavaScript, Practical Extraction Report Language (PERL), HypertextPre-Processor (PHP), pipes, Python, wireless application protocol (WAP),WebObjects®, and/or the like. The information server may support securecommunications protocols such as, but not limited to, File TransferProtocol (FTP); HyperText Transfer Protocol (HTTP); Secure HypertextTransfer Protocol (HTTPS), Secure Socket Layer (SSL), messagingprotocols (e.g., America Online (AOL) Instant Messenger (AIM)®,Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), MicrosoftNetwork (MSN) Messenger® Service, Presence and Instant MessagingProtocol (PRIM), Internet Engineering Task Force's® (IETF's) SessionInitiation Protocol (SIP), SIP for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), open XML-based Extensible Messaging andPresence Protocol (XMPP) (i.e., Jabber® or Open Mobile Alliance's(OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! InstantMessenger® Service, and/or the like. The information server providesresults in the form of Web pages to Web browsers, and allows for themanipulated generation of the Web pages through interaction with otherprogram components. After a Domain Name System (DNS) resolution portionof an HTTP request is resolved to a particular information server, theinformation server resolves requests for information at specifiedlocations on the ARTID controller based on the remainder of the HTTPrequest. For example, a request such ashttp://123.124.125.126/myInformation.html might have the IP portion ofthe request “123.124.125.126” resolved by a DNS server to an informationserver at that IP address; that information server might in turn furtherparse the http request for the “/myInformation.html” portion of therequest and resolve it to a location in memory containing theinformation “myInformation.html.” Additionally, other informationserving protocols may be employed across various ports, e.g., FTPcommunications across port 21, and/or the like. An information servermay communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the information server communicates with the ARTID database1219, operating systems, other program components, user interfaces, Webbrowsers, and/or the like.

Access to the ARTID database may be achieved through a number ofdatabase bridge mechanisms such as through scripting languages asenumerated below (e.g., CGI) and through inter-application communicationchannels as enumerated below (e.g., CORBA, WebObjects, etc.). Any datarequests through a Web browser are parsed through the bridge mechanisminto appropriate grammars as required by the ARTID. In one embodiment,the information server would provide a Web form accessible by a Webbrowser. Entries made into supplied fields in the Web form are tagged ashaving been entered into the particular fields, and parsed as such. Theentered terms are then passed along with the field tags, which act toinstruct the parser to generate queries directed to appropriate tablesand/or fields. In one embodiment, the parser may generate queries in SQLby instantiating a search string with the proper join/select commandsbased on the tagged text entries, wherein the resulting command isprovided over the bridge mechanism to the ARTID as a query. Upongenerating query results from the query, the results are passed over thebridge mechanism, and may be parsed for formatting and generation of anew results Web page by the bridge mechanism. Such a new results Webpage is then provided to the information server, which may supply it tothe requesting Web browser.

Also, an information server may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

User Interface

Computer interfaces in some respects are similar to automobile operationinterfaces. Automobile operation interface elements such as steeringwheels, gearshifts, and speedometers facilitate the access, operation,and display of automobile resources, and status. Computer interactioninterface elements such as buttons, check boxes, cursors, menus,scrollers, and windows (collectively referred to as widgets) similarlyfacilitate the access, capabilities, operation, and display of data andcomputer hardware and operating system resources, and status. Operationinterfaces are called user interfaces. Graphical user interfaces (GUIs)such as the Apple's iOS®, Macintosh Operating System's Aqua®; IBM'sOS/2®; Google's Chrome® (e.g., and other webbrowser/cloud based clientOSs); Microsoft's Windows® varied UIs2000/2003/3.1/95/98/CE/Millenium/Mobile/NT/Vista/XP (Server) (i.e.,Aero, Surface, etc.); Unix's X-Windows (e.g., which may includeadditional Unix graphic interface libraries and layers such as K DesktopEnvironment (KDE), mythTV and GNU Network Object Model Environment(GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH,Java, JavaScript, etc. interface libraries such as, but not limited to,Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject,Yahoo! User Interface®, any of which may be used and) provide a baselineand means of accessing and displaying information graphically to users.

A user interface component 1217 is a stored program component that isexecuted by a CPU. The user interface may be a graphic user interface asprovided by, with, and/or atop operating systems and/or operatingenvironments such as already discussed. The user interface may allow forthe display, execution, interaction, manipulation, and/or operation ofprogram components and/or system facilities through textual and/orgraphical facilities. The user interface provides a facility throughwhich users may affect, interact, and/or operate a computer system. Auser interface may communicate to and/or with other components in acomponent collection, including itself, and/or facilities of the like.Most frequently, the user interface communicates with operating systems,other program components, and/or the like. The user interface maycontain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Web Browser

A Web browser component 1218 is a stored program component that isexecuted by a CPU. The Web browser may be a hypertext viewingapplication such as Apple's (mobile) Safari®, Google's Chrome®,Microsoft Internet Explorer®, Mozilla's Firefox®, Netscape Navigator®,and/or the like. Secure Web browsing may be supplied with 128 bit (orgreater) encryption by way of HTTPS, SSL, and/or the like. Web browsersallowing for the execution of program components through facilities suchas ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-inAPIs (e.g., FireFox®, Safari® Plug-in, and/or the like APIs), and/or thelike. Web browsers and like information access tools may be integratedinto PDAs, cellular telephones, and/or other mobile devices. A Webbrowser may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the Web browser communicates with information servers,operating systems, integrated program components (e.g., plug-ins),and/or the like; e.g., it may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses. Also, in place of a Webbrowser and information server, a combined application may be developedto perform similar operations of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the ARTID enabled nodes. Thecombined application may be nugatory on systems employing Web browsers.

Mail Server

A mail server component 1221 is a stored program component that isexecuted by a CPU 1203. The mail server may be an Internet mail serversuch as, but not limited to: dovecot, Courier IMAP, Cyrus IMAP, Maildir,Microsoft Exchange, sendmail, and/or the like. The mail server may allowfor the execution of program components through facilities such as ASP,ActiveX, (ANSI) (Objective-) C (++), C # and/or .NET, CGI scripts, Java,JavaScript, PERL, PHP, pipes, Python, WebObjects®, and/or the like. Themail server may support communications protocols such as, but notlimited to: Internet message access protocol (IMAP), MessagingApplication Programming Interface (MAPI)/Microsoft Exchange, post officeprotocol (POPS), simple mail transfer protocol (SMTP), and/or the like.The mail server can route, forward, and process incoming and outgoingmail messages that have been sent, relayed and/or otherwise traversingthrough and/or to the ARTID. Alternatively, the mail server componentmay be distributed out to mail service providing entities such asGoogle's® cloud services (e.g., Gmail and notifications mayalternatively be provided via messenger services such as AOL's InstantMessenger®, Apple's iMessage®, Google Messenger®, SnapChat®, etc.).

Access to the ARTID mail may be achieved through a number of APIsoffered by the individual Web server components and/or the operatingsystem.

Also, a mail server may contain, communicate, generate, obtain, and/orprovide program component, system, user, and/or data communications,requests, information, and/or responses.

Mail Client

A mail client component 1222 is a stored program component that isexecuted by a CPU 1203. The mail client may be a mail viewingapplication such as Apple Mail®, Microsoft Entourage®, MicrosoftOutlook®, Microsoft Outlook Express®, Mozilla®, Thunderbird®, and/or thelike. Mail clients may support a number of transfer protocols, such as:IMAP, Microsoft Exchange, POPS, SMTP, and/or the like. A mail client maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, themail client communicates with mail servers, operating systems, othermail clients, and/or the like; e.g., it may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, information, and/or responses. Generally,the mail client provides a facility to compose and transmit electronicmail messages.

Cryptographic Server

A cryptographic server component 1220 is a stored program component thatis executed by a CPU 1203, cryptographic processor 1226, cryptographicprocessor interface 1227, cryptographic processor device 1228, and/orthe like. Cryptographic processor interfaces will allow for expeditionof encryption and/or decryption requests by the cryptographic component;however, the cryptographic component, alternatively, may run on a CPU.The cryptographic component allows for the encryption and/or decryptionof provided data. The cryptographic component allows for both symmetricand asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/ordecryption. The cryptographic component may employ cryptographictechniques such as, but not limited to: digital certificates (e.g.,X.509 authentication framework), digital signatures, dual signatures,enveloping, password access protection, public key management, and/orthe like. The cryptographic component will facilitate numerous(encryption and/or decryption) security protocols such as, but notlimited to: checksum, Data Encryption Standard (DES), Elliptical CurveEncryption (ECC), International Data Encryption Algorithm (IDEA),Message Digest 5 (MD5, which is a one way hash operation), passwords,Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption andauthentication system that uses an algorithm developed in 1977 by RonRivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA),Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS),Transport Layer Security (TLS), and/or the like. Employing suchencryption security protocols, the ARTID may encrypt all incoming and/oroutgoing communications and may serve as node within a virtual privatenetwork (VPN) with a wider communications network. The cryptographiccomponent facilitates the process of “security authorization” wherebyaccess to a resource is inhibited by a security protocol wherein thecryptographic component effects authorized access to the securedresource. In addition, the cryptographic component may provide uniqueidentifiers of content, e.g., employing and MD5 hash to obtain a uniquesignature for an digital audio file. A cryptographic component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. The cryptographiccomponent supports encryption schemes allowing for the securetransmission of information across a communications network to allow theARTID component to engage in secure transactions if so desired. Thecryptographic component facilitates the secure accessing of resources onthe ARTID and facilitates the access of secured resources on remotesystems; i.e., it may act as a client and/or server of securedresources. Most frequently, the cryptographic component communicateswith information servers, operating systems, other program components,and/or the like. The cryptographic component may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, and/or responses.

The ARTID Database

The ARTID database component 1219 may be embodied in a database and itsstored data. The database is a stored program component, which isexecuted by the CPU; the stored program component portion configuringthe CPU to process the stored data. The database may be a faulttolerant, relational, scalable, secure database such as MySQL®, Oracle®,Sybase®, etc. may be used. Additionally, optimized fast memory anddistributed databases such as IBM's Netezza®, MongoDB's MongoDB®,opensource Hadoop®, opensource VoltDB, SAP's Hana®, etc. Relationaldatabases are an extension of a flat file. Relational databases consistof a series of related tables. The tables are interconnected via a keyfield. Use of the key field allows the combination of the tables byindexing against the key field; i.e., the key fields act as dimensionalpivot points for combining information from various tables.Relationships generally identify links maintained between tables bymatching primary keys. Primary keys represent fields that uniquelyidentify the rows of a table in a relational database. Alternative keyfields may be used from any of the fields having unique value sets, andin some alternatives, even non-unique values in combinations with otherfields. More precisely, they uniquely identify rows of a table on the“one” side of a one-to-many relationship.

Alternatively, the ARTID database may be implemented using various otherdata-structures, such as an array, hash, (linked) list, struct,structured text file (e.g., XML), table, and/or the like. Suchdata-structures may be stored in memory and/or in (structured) files. Inanother alternative, an object-oriented database may be used, such asFrontier™, ObjectStore, Poet, Zope, and/or the like. Object databasescan include a number of object collections that are grouped and/orlinked together by common attributes; they may be related to otherobject collections by some common attributes. Object-oriented databasesperform similarly to relational databases with the exception thatobjects are not just pieces of data but may have other types ofcapabilities encapsulated within a given object. If the ARTID databaseis implemented as a data-structure, the use of the ARTID database 1219may be integrated into another component such as the ARTID component1235. Also, the database may be implemented as a mix of data structures,objects, and relational structures. Databases may be consolidated and/ordistributed in countless variations (e.g., see Distributed ARTID below).Portions of databases, e.g., tables, may be exported and/or imported andthus decentralized and/or integrated.

In one embodiment, the database component 1219 includes several tables1219 a-z:

An accounts table 1219 a includes fields such as, but not limited to: anaccountID, accountOwnerID, accountContactID, assetIDs, deviceIDs,paymentIDs, transactionIDs, userIDs, accountType (e.g., agent, entity(e.g., corporate, non-profit, partnership, etc.), individual, etc.),accountCreationDate, accountUpdateDate, accountName, accountNumber,routingNumber, linkWalletsID, accountPrioritAccaountRatio,accountAddress, accountState, accountZIPcode, accountCountry,accountEmail, accountPhone, accountAuthKey, accountIPaddress,accountURLAccessCode, accountPortNo, accountAuthorizationCode,accountAccessPrivileges, accountPreferences, accountRestrictions, and/orthe like;

A users table 1219 b includes fields such as, but not limited to: auserID, userSSN, taxID, userContactID, accountID, assetIDs, deviceIDs,paymentIDs, transactionIDs, userType (e.g., agent, entity (e.g.,corporate, non-profit, partnership, etc.), individual, etc.),namePrefix, firstName, middleName, lastName, nameSuffix, DateOfBirth,userAge, userName, userEmail, userSocialAccountID, contactType,contactRelationship, userPhone, userAddress, userCity, userState,userZIPCode, userCountry, userAuthorizationCode, userAccessPrivilges,userPreferences, userRestrictions, and/or the like (the user table maysupport and/or track multiple entity accounts on a ARTID);

An devices table 1219 c includes fields such as, but not limited to:deviceID, sensorIDs, accountID, assetIDs, paymentIDs, deviceType,deviceName, deviceManufacturer, deviceModel, deviceVersion,deviceSerialNo, deviceIPaddress, deviceMACaddress, device_ECID,deviceUUID, deviceLocation, deviceCertificate, deviceOS, appIDs,deviceResources, deviceSession, authKey, deviceSecureKey,walletAppInstalledFlag, deviceAccessPrivileges, devicePreferences,deviceRestrictions, hardware_config, software_config, storage_location,sensor_value, pin_reading, data_length, channel_requirement,sensor_name, sensor_model_no, sensor_manufacturer, sensor_type,sensor_serial_number, sensor_power_requirement,device_power_requirement, location, sensor_associated_tool,sensor_dimensions, device_dimensions, sensor_communications_type,device_communications_type, power_percentage, power_condition,temperature_setting, speed_adjust, hold_duration, part_actuation, and/orthe like. Device table may, in some embodiments, include fieldscorresponding to one or more Bluetooth profiles, such as those publishedat https://www.bluetooth.org/en-us/specification/adopted-specifications,and/or other device specifications, and/or the like;

An apps table 1219 d includes fields such as, but not limited to: appID,appName, appType, appDependencies, accountID, deviceIDs, transactionID,userID, appStoreAuthKey, appStoreAccountID, appStoreIPaddress,appStoreURLaccessCode, appStorePortNo, appAccessPrivileges,appPreferences, appRestrictions, portNum, access_API_call,linked_wallets_list, and/or the like;

An assets table 1219 e includes fields such as, but not limited to:assetID, accountID, userID, distributorAccountID, distributorPaymentID,distributorOnwerID, assetOwnerID, assetType, assetSourceDeviceID,assetSourceDeviceType, assetSourceDeviceName,assetSourceDistributionChannelID, assetSourceDistributionChannelType,assetSourceDistributionChannelName, assetTargetChannelID,assetTargetChannelType, assetTargetChannelName, assetName,assetSeriesName, assetSeriesSeason, assetSeriesEpisode, assetCode,assetQuantity, assetCost, assetPrice, assetValue, assetManufactuer,assetModelNo, assetSerialNo, assetLocation, assetAddress, assetState,assetZIPcode, assetState, assetCountry, assetEmail, assetIPaddress,assetURLaccessCode, assetOwnerAccountID, subscriptionIDs,assetAuthroizationCode, assetAccessPrivileges, assetPreferences,assetRestrictions, assetAPI, assetAPIconnectionAddress, and/or the like;

A payments table 1219 f includes fields such as, but not limited to:paymentID, accountID, userID, couponID, couponValue, couponConditions,couponExpiration, paymentType, paymentAccountNo, paymentAccountName,paymentAccountAuthorizationCodes, paymentExpirationDate, paymentCCV,paymentRoutingNo, paymentRoutingType, paymentAddress, paymentState,paymentZIPcode, paymentCountry, paymentEmail, paymentAuthKey,paymentIPaddress, paymentURLaccessCode, paymentPortNo,paymentAccessPrivileges, paymentPreferences, payementRestrictions,and/or the like;

An transactions table 1219 g includes fields such as, but not limitedto: transactionID, accountID, assetIDs, deviceIDs, paymentIDs,transactionIDs, userID, merchantID, transactionType, transactionDate,transactionTime, transactionAmount, transactionQuantity,transactionDetails, productsList, productType, productTitle,productsSummary, productParamsList, transactionNo,transactionAccessPrivileges, transactionPreferences,transactionRestrictions, merchantAuthKey, merchantAuthCode, and/or thelike;

An merchants table 1219 h includes fields such as, but not limited to:merchantID, merchantTaxID, merchanteName, merchantContactUserID,accountID, issuerID, acquirerID, merchantEmail, merchantAddress,merchantState, merchantZIPcode, merchantCountry, merchantAuthKey,merchantIPaddress, portNum, merchantURLaccessCode, merchantPortNo,merchantAccessPrivileges, merchantPreferences, merchantRestrictions,and/or the like;

An ads table 1219 i includes fields such as, but not limited to: adID,advertiserID, adMerchantID, adNetworkID, adName, adTags, advertiserName,adSponsor, adTime, adGeo, adAttributes, adFormat, adProduct, adText,adMedia, adMediaID, adChannelID, adTagTime, adAudioSignature, adHash,adTemplateID, adTemplateData, adSourceID, adSourceName,adSourceServerIP, adSourceURL, adSourceSecurityProtocol, adSourceFTP,adAuthKey, adAccessPrivileges, adPreferences, adRestrictions,adNetworkXchangeID, adNetworkXchangeName, adNetworkXchangeCost,adNetworkXchangeMetricType (e.g., CPA, CPC, CPM, CTR, etc.),adNetworkXchangeMetricValue, adNetworkXchangeServer,adNetworkXchangePortNumber, publisherID, publisherAddress, publisherURL,publisherTag, publisherIndustry, publisherName, publisherDescripLion,siteDomain, siteURL, siteContent, siteTag, siteContext, sitelmpression,siteVisits, siteHeadline, sitePage, siteAdPrice, sitePlacement,sitePosition, bidID, bidExchange, bidOS, bidTarget, bidTimestamp,bidPrice, bidlmpressionID, bidType, bidScore, adType (e.g., mobile,desktop, wearable, largescreen, interstitial, etc.), assetID,merchantID, deviceID, userID, accountID, impressionID, impressionOS,impressionTimeStamp, impressionGeo, impressionAction, impressionType,impressionPublisherID, impressionPublisherURL, and/or the like;

A market_data table 1219 z includes fields such as, but not limited to:market_data_feed_ID, asset_ID, asset_symbol, asset_name, spot_price,bid_price, ask_price, and/or the like; in one embodiment, the marketdata table is populated through a market data feed (e.g., Bloomberg'sPhatPipe®, Consolidated Quote System® (CQS), Consolidated TapeAssociation® (CTA), Consolidated Tape System® (CTS), Dun & Bradstreet®,OTC Montage Data Feed® (OMDF), Reuter's Tib®, Triarch®, US equity tradeand quote market Data®, Unlisted Trading Privileges® (UTP) Trade DataFeed® (UTDF), UTP Quotation Data Feed® (UQDF), and/or the like feeds,e.g., via ITC 2.1 and/or respective feed protocols), for example,through Microsoft's® Active Template Library and Dealing ObjectTechnology's real-time toolkit Rtt.Multi.

In one embodiment, the ARTID database may interact with other databasesystems. For example, employing a distributed database system, queriesand data access by search ARTID component may treat the combination ofthe ARTID database, an integrated data security layer database as asingle database entity (e.g., see Distributed ARTID below).

In one embodiment, user programs may contain various user interfaceprimitives, which may serve to update the ARTID. Also, various accountsmay require custom database tables depending upon the environments andthe types of clients the ARTID may need to serve. It should be notedthat any unique fields may be designated as a key field throughout. Inan alternative embodiment, these tables have been decentralized intotheir own databases and their respective database controllers (i.e.,individual database controllers for each of the above tables). Employingvarious data processing techniques, one may further distribute thedatabases over several computer systemizations and/or storage devices.Similarly, configurations of the decentralized database controllers maybe varied by consolidating and/or distributing the various databasecomponents 1219 a-z. The ARTID may be configured to keep track ofvarious settings, inputs, and parameters via database controllers.

The ARTID database may communicate to and/or with other components in acomponent collection, including itself, and/or facilities of the like.Most frequently, the ARTID database communicates with the ARTIDcomponent, other program components, and/or the like. The database maycontain, retain, and provide information regarding other nodes and data.

The ARTIDs

The ARTID component 1235 is a stored program component that is executedby a CPU. In one embodiment, the ARTID component incorporates any and/orall combinations of the aspects of the ARTID that was discussed in theprevious figures. As such, the ARTID affects accessing, obtaining andthe provision of information, services, transactions, and/or the likeacross various communications networks. The features and embodiments ofthe ARTID discussed herein increase network efficiency by reducing datatransfer requirements the use of more efficient data structures andmechanisms for their transfer and storage. As a consequence, more datamay be transferred in less time, and latencies with regard totransactions, are also reduced. In many cases, such reduction instorage, transfer time, bandwidth requirements, latencies, etc., willreduce the capacity and structural infrastructure requirements tosupport the ARTID's features and facilities, and in many cases reducethe costs, energy consumption/requirements, and extend the life ofARTID's underlying infrastructure; this has the added benefit of makingthe ARTID more reliable. Similarly, many of the features and mechanismsare designed to be easier for users to use and access, therebybroadening the audience that may enjoy/employ and exploit the featuresets of the ARTID; such ease of use also helps to increase thereliability of the ARTID. In addition, the feature sets includeheightened security as noted via the Cryptographic components 1220,1226, 1228 and throughout, making access to the features and data morereliable and secure

The ARTID transforms PIN, unique user identifying device datastructureinputs, via ARTID components (e.g., EMV APDU), into secure paymentauthorization outputs.

The ARTID component enabling access of information between nodes may bedeveloped by employing various development tools and languages such as,but not limited to: Apache® components, Assembly, ActiveX, binaryexecutables, (ANSI) (Objective-) C (++), C # and/or .NET, databaseadapters, CGI scripts, Java, JavaScript, mapping tools, procedural andobject oriented development tools, PERL, PHP, Python, shell scripts, SQLcommands, web application server extensions, web developmentenvironments and libraries (e.g., Microsoft's® ActiveX; Adobe® AIR, FLEX& FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools;Prototype; script.aculo.us; Simple Object Access Protocol (SOAP);SWFObject; Yahoo!® User Interface; and/or the like), WebObjects®, and/orthe like. In one embodiment, the ARTID server employs a cryptographicserver to encrypt and decrypt communications. The ARTID component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, theARTID component communicates with the ARTID database, operating systems,other program components, and/or the like. The ARTID may contain,communicate, generate, obtain, and/or provide program component, system,user, and/or data communications, requests, and/or responses.

Distributed ARTIDs

The structure and/or operation of any of the ARTID node controllercomponents may be combined, consolidated, and/or distributed in anynumber of ways to facilitate development and/or deployment. Similarly,the component collection may be combined in any number of ways tofacilitate deployment and/or development. To accomplish this, one mayintegrate the components into a common code base or in a facility thatcan dynamically load the components on demand in an integrated fashion.As such a combination of hardware may be distributed within a location,within a region and/or globally where logical access to a controller maybe abstracted as a singular node, yet where a multitude of private,semiprivate and publically accessible node controllers (e.g., viadispersed data centers) are coordinated to serve requests (e.g.,providing private cloud, semi-private cloud, and public cloud computingresources) and allowing for the serving of such requests in discreteregions (e.g., isolated, local, regional, national, global cloudaccess).

The component collection may be consolidated and/or distributed incountless variations through various data processing and/or developmenttechniques. Multiple instances of any one of the program components inthe program component collection may be instantiated on a single node,and/or across numerous nodes to improve performance throughload-balancing and/or data-processing techniques. Furthermore, singleinstances may also be distributed across multiple controllers and/orstorage devices; e.g., databases. All program component instances andcontrollers working in concert may do so through various data processingcommunication techniques.

The configuration of the ARTID controller will depend on the context ofsystem deployment. Factors such as, but not limited to, the budget,capacity, location, and/or use of the underlying hardware resources mayaffect deployment requirements and configuration. Regardless of if theconfiguration results in more consolidated and/or integrated programcomponents, results in a more distributed series of program components,and/or results in some combination between a consolidated anddistributed configuration, data may be communicated, obtained, and/orprovided. Instances of components consolidated into a common code basefrom the program component collection may communicate, obtain, and/orprovide data. This may be accomplished through intra-application dataprocessing communication techniques such as, but not limited to: datareferencing (e.g., pointers), internal messaging, object instancevariable communication, shared memory space, variable passing, and/orthe like. For example, cloud services such as Amazon Data Services®,Microsoft Azure®, Hewlett Packard Helion®, IBM® Cloud services allow forARTID controller and/or ARTID component collections to be hosted in fullor partially for varying degrees of scale.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other component components may be accomplishedthrough inter-application data processing communication techniques suchas, but not limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), Jini local and remote applicationprogram interfaces, JavaScript Object Notation (JSON), Remote MethodInvocation (RMI), SOAP, process pipes, shared files, and/or the like.Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of anHTTP post command, e.g.:

w3c -post http://... Value1

where Value1 is discerned as being a parameter because “http://” is partof the grammar syntax, and what follows is considered part of the postvalue. Similarly, with such a grammar, a variable “Value1” may beinserted into an “http://” post command and then sent. The grammarsyntax itself may be presented as structured data that is interpretedand/or otherwise used to generate the parsing mechanism (e.g., a syntaxdescription text file as processed by lex, yacc, etc.). Also, once theparsing mechanism is generated and/or instantiated, it itself mayprocess and/or parse structured data such as, but not limited to:character (e.g., tab) delineated text, HTML, structured text streams,XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or parsers (e.g., JSON, SOAP, and/or like parsers) thatmay be employed to parse (e.g., communications) data. Further, theparsing grammar may be used beyond message parsing, but may also be usedto parse: databases, data collections, data stores, structured data,and/or the like. Again, the desired configuration will depend upon thecontext, environment, and requirements of system deployment.

For example, in some implementations, the ARTID controller may beexecuting a PHP script implementing a Secure Sockets Layer (“SSL”)socket server via the information server, which listens to incomingcommunications on a server port to which a client may send data, e.g.,data encoded in JSON format. Upon identifying an incoming communication,the PHP script may read the incoming message from the client device,parse the received JSON-encoded text data to extract information fromthe JSON-encoded text data into PHP script variables, and store the data(e.g., client identifying information, etc.) and/or extractedinformation in a relational database accessible using the StructuredQuery Language (“SQL”). An exemplary listing, written substantially inthe form of PHP/SQL commands, to accept JSON-encoded input data from aclient device via a SSL connection, parse the data to extract variables,and store the data to a database, is provided below:

<?PHP header(′Content-Type: text/plain′); // set ip address and port tolisten to for incoming data $address = ‘192.168.0.100’; $port = 255; //create a server-side SSL socket, listen for/accept incomingcommunication $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); // read input datafrom client device in 1024 byte blocks until end of message do { $input= “”; $input = socket_read($client, 1024); $data .= $input; }while($input != “”); // parse data to extract variables $obj =json_decode($data, true); // store input data in a databasemysql_connect(″201.408.185.132″,$DBserver,$password); // access databaseserver mysql_select(″CLIENT_DB.SQL″); // select database to appendmysql_query(“INSERT INTO UserTable (transmission) VALUES ($data)”); //add data to UserTable table in a CLIENT databasemysql_close(″CLIENT_DB.SQL″); // close connection to database ?>

Also, the following resources may be used to provide example embodimentsregarding SOAP parser implementation:

http://www.xav.com/perl/site/lib/SOAP/Parser.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htmand other parser implementations:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htmall of which are hereby expressly incorporated by reference.

In order to address various issues and advance the art, the entirety ofthis application for Antifraud Resilient Transaction IdentifierDatastructure Apparatuses, Methods and Systems (including the CoverPage, Title, Headings, Field, Background, Summary, Brief Description ofthe Drawings, Detailed Description, Claims, Abstract, Figures,Appendices, and otherwise) shows, by way of illustration, variousembodiments in which the claimed innovations may be practiced. Theadvantages and features of the application are of a representativesample of embodiments only, and are not exhaustive and/or exclusive.They are presented only to assist in understanding and teach the claimedprinciples. It should be understood that they are not representative ofall claimed innovations. As such, certain aspects of the disclosure havenot been discussed herein. That alternate embodiments may not have beenpresented for a specific portion of the innovations or that furtherundescribed alternate embodiments may be available for a portion is notto be considered a disclaimer of those alternate embodiments. It will beappreciated that many of those undescribed embodiments incorporate thesame principles of the innovations and others are equivalent. Thus, itis to be understood that other embodiments may be utilized andfunctional, logical, operational, organizational, structural and/ortopological modifications may be made without departing from the scopeand/or spirit of the disclosure. As such, all examples and/orembodiments are deemed to be non-limiting throughout this disclosure.Further and to the extent any financial and/or investment examples areincluded, such examples are for illustrative purpose(s) only, and arenot, nor should they be interpreted, as investment advice. Also, noinference should be drawn regarding those embodiments discussed hereinrelative to those not discussed herein other than it is as such forpurposes of reducing space and repetition. For instance, it is to beunderstood that the logical and/or topological structure of anycombination of any program components (a component collection), othercomponents, data flow order, logic flow order, and/or any presentfeature sets as described in the figures and/or throughout are notlimited to a fixed operating order and/or arrangement, but rather, anydisclosed order is exemplary and all equivalents, regardless of order,are contemplated by the disclosure. Similarly, descriptions ofembodiments disclosed throughout this disclosure, any reference todirection or orientation is merely intended for convenience ofdescription and is not intended in any way to limit the scope ofdescribed embodiments. Relative terms such as “lower”, “upper”,“horizontal”, “vertical”, “above”, “below”, “up”, “down”, “top” and“bottom” as well as derivative thereof (e.g., “horizontally”,“downwardly”, “upwardly”, etc.) should not be construed to limitembodiments, and instead, again, are offered for convenience ofdescription of orientation. These relative descriptors are forconvenience of description only and do not require that any embodimentsbe constructed or operated in a particular orientation unless explicitlyindicated as such. Terms such as “attached”, “affixed”, “connected”,“coupled”, “interconnected”, and similar may refer to a relationshipwherein structures are secured or attached to one another eitherdirectly or indirectly through intervening structures, as well as bothmovable or rigid attachments or relationships, unless expresslydescribed otherwise. Furthermore, it is to be understood that suchfeatures are not limited to serial execution, but rather, any number ofthreads, processes, services, servers, and/or the like that may executeasynchronously, concurrently, in parallel, simultaneously,synchronously, and/or the like are contemplated by the disclosure. Assuch, some of these features may be mutually contradictory, in that theycannot be simultaneously present in a single embodiment. Similarly, somefeatures are applicable to one aspect of the innovations, andinapplicable to others. In addition, the disclosure includes otherinnovations not presently claimed. Applicant reserves all rights inthose presently unclaimed innovations including the right to claim suchinnovations, file additional applications, continuations, continuationsin part, divisions, and/or the like thereof. As such, it should beunderstood that advantages, embodiments, examples, functional, features,logical, operational, organizational, structural, topological, and/orother aspects of the disclosure are not to be considered limitations onthe disclosure as defined by the claims or limitations on equivalents tothe claims. It is to be understood that, depending on the particularneeds and/or characteristics of a ARTID individual and/or enterpriseuser, database configuration and/or relational model, data type, datatransmission and/or network framework, syntax structure, and/or thelike, various embodiments of the ARTID, may be implemented that allow agreat deal of flexibility and customization. For example, aspects of theARTID may be adapted for credential security. While various embodimentsand discussions of the ARTID have included data security, however, it isto be understood that the embodiments described herein may be readilyconfigured and/or customized for a wide variety of other applicationsand/or implementations.

What is claimed is:
 1. A virtual secure element datastructuretransaction apparatus, comprising: a memory; a component collection inthe memory; a processor disposed in communication with the memory, andconfigured to issue a plurality of processing instructions from thecomponent collection stored in the memory, to: obtain request togenerate a tamper resistant asset account from a requestor, wherein therequest includes a requestor identifier and a unique requestor deviceidentifier, wherein the requestor identifier includes any of: requestorname, requestor address, account identifier, requestor, phone number,social security number, wherein the unique requestor device identifierincludes any of: UUID, storage device unique identifier, uniqueoperating system identifiers, cryptographic signature of the device,cryptographic hashes of any of: the unique requestor device identifierand the requestor identifier; instantiate a new tamper resistant assetaccount, wherein the account is populated with the requestor identifier,unique requestor device identifier, a secure cryptographic element forthe tamper resistant account, provide a message to generate an accountcard associated with the tamper resistant asset account, wherein theaccount card is configured to authorize account access to the useraccess credential, obtain a request to engage the account card in atransaction, wherein the request includes the user access credential;generate a card access event message from the request to engage theaccount card, wherein the card access event message is an equivalent ofa card present chip engagement to the user access credential; providethe card access event message to a payment network; obtain a card accessevent authorization response.
 2. The apparatus of claim 1, wherein theaccount card is a new physical account.
 3. The apparatus of claim 1,wherein the account card is a virtual account card.
 4. The apparatus ofclaim 1, wherein the account card is a new physical account card and anassociated virtual account card associated with the tamper resistantasset account.
 5. The apparatus of claim 4, wherein the message isconfigured to generate the virtual account card to be a clone of thephysical account card.
 6. The apparatus of claim 5, wherein the physicalaccount card and virtual account card have the same account number, asame secure cryptographic element.
 7. The apparatus of claim 1, whereinthe card access event message is configured to be delivered to an issuerof the physical account card.
 8. The apparatus of claim 1, further,comprising: obtaining a secure element update request; providing amessage to generate a new secure cryptographic element and update thesame secure cryptographic element.
 9. The apparatus of claim 1, whereinthe message to generate a new secure cryptographic element may betriggered periodically, and wherein a period may be any of: seconds,minutes, hours, days, weeks, months, years, dynamically, on-demand,real-time.
 10. A processor-readable virtual secure element datastructuretransaction non-transient medium storing processor-executablecomponents, the components, comprising: a component collection stored inthe medium, including processor executable instructions to: obtainrequest to generate a tamper resistant asset account from a requestor,wherein the request includes a requestor identifier and a uniquerequestor device identifier, wherein the requestor identifier includesany of: requestor name, requestor address, account identifier,requestor, phone number, social security number, wherein the uniquerequestor device identifier includes any of: UUID, storage device uniqueidentifier, unique operating system identifiers, cryptographic signatureof the device, cryptographic hashes of any of: the unique requestordevice identifier and the requestor identifier; instantiate a new tamperresistant asset account, wherein the account is populated with therequestor identifier, unique requestor device identifier, a securecryptographic element for the tamper resistant account, provide amessage to generate an account card associated with the tamper resistantasset account, wherein the account card is configured to authorizeaccount access to the user access credential, obtain a request to engagethe account card in a transaction, wherein the request includes the useraccess credential; generate a card access event message from the requestto engage the account card, wherein the card access event message is anequivalent of a card present chip engagement to the user accesscredential; provide the card access event message to a payment network;obtain a card access event authorization response.
 11. The apparatus ofclaim 10, wherein the account card is a new physical account card and anassociated virtual account card associated with the tamper resistantasset account.
 12. The apparatus of claim 4, wherein the message isconfigured to generate the virtual account card to be a clone of thephysical account card.
 13. A processor-implemented virtual secureelement datastructure transaction system, comprising: means to obtainrequest to generate a tamper resistant asset account from a requestor,wherein the request includes a requestor identifier and a uniquerequestor device identifier, wherein the requestor identifier includesany of: requestor name, requestor address, account identifier,requestor, phone number, social security number, wherein the uniquerequestor device identifier includes any of: UUID, storage device uniqueidentifier, unique operating system identifiers, cryptographic signatureof the device, cryptographic hashes of any of: the unique requestordevice identifier and the requestor identifier; means to instantiate anew tamper resistant asset account, wherein the account is populatedwith the requestor identifier, unique requestor device identifier, asecure cryptographic element for the tamper resistant account, means toprovide a message to generate an account card associated with the tamperresistant asset account, wherein the account card is configured toauthorize account access to the user access credential, means to obtaina request to engage the account card in a transaction, wherein therequest includes the user access credential; means to generate a cardaccess event message from the request to engage the account card,wherein the card access event message is an equivalent of a card presentchip engagement to the user access credential; means to provide the cardaccess event message to a payment network; means to obtain a card accessevent authorization response.
 14. The apparatus of claim 13, wherein theaccount card is a new physical account card and an associated virtualaccount card associated with the tamper resistant asset account.
 15. Theapparatus of claim, wherein the message is configured to generate thevirtual account card to be a clone of the physical account card.
 16. Aprocessor-implemented virtual secure element datastructure transactionmethod, comprising: executing processor-implemented component collectioninstructions to: obtain request to generate a tamper resistant assetaccount from a requestor, wherein the request includes a requestoridentifier and a unique requestor device identifier, wherein therequestor identifier includes any of: requestor name, requestor address,account identifier, requestor, phone number, social security number,wherein the unique requestor device identifier includes any of: UUID,storage device unique identifier, unique operating system identifiers,cryptographic signature of the device, cryptographic hashes of any of:the unique requestor device identifier and the requestor identifier;instantiate a new tamper resistant asset account, wherein the account ispopulated with the requestor identifier, unique requestor deviceidentifier, a secure cryptographic element for the tamper resistantaccount, provide a message to generate an account card associated withthe tamper resistant asset account, wherein the account card isconfigured to authorize account access to the user access credential,obtain a request to engage the account card in a transaction, whereinthe request includes the user access credential; generate a card accessevent message from the request to engage the account card, wherein thecard access event message is an equivalent of a card present chipengagement to the user access credential; provide the card access eventmessage to a payment network; obtain a card access event authorizationresponse.
 17. The apparatus of claim 13, wherein the account card is anew physical account card and an associated virtual account cardassociated with the tamper resistant asset account.
 18. The apparatus ofclaim 4, wherein the message is configured to generate the virtualaccount card to be a clone of the physical account card.
 19. A virtualsecure element datastructure transaction apparatus, comprising: amemory; a component collection in the memory; a processor disposed incommunication with the memory, and configured to issue a plurality ofprocessing instructions from the component collection stored in thememory, to: obtain request to generate a tamper resistant asset accountfrom a requestor, wherein the request includes a requestor identifierand a unique requestor device identifier, wherein the requestoridentifier includes any of: requestor name, requestor address, accountidentifier, requestor, phone number, social security number, wherein theunique requestor device identifier includes any of: UUID, storage deviceunique identifier, unique operating system identifiers, cryptographicsignature of the device, cryptographic hashes of any of: the uniquerequestor device identifier and the requestor identifier; instantiate anew tamper resistant asset account, wherein the account is populatedwith the requestor identifier, unique requestor device identifier, asecure cryptographic element for the tamper resistant account, provide amessage to generate a new physical account card and an associatedvirtual account card associated with the tamper resistant asset account,wherein the message is configured to generate the virtual account cardto be a clone of the physical account card, wherein the physical accountcard and virtual account card have the same account number, a samesecure cryptographic element, wherein the physical account card and thevirtual account card are configured to authorize account access to asame user access credential; obtain a request to engage the virtualaccount card in a transaction, wherein the request includes the useraccess credential; generate a card access event message from the requestto engage the virtual account card, wherein the card access eventmessage is an equivalent of a card present chip engagement to the useraccess credential; provide the card access event message to a paymentnetwork; obtain a card access event authorization response.
 20. Theapparatus of claim 19, wherein the card access event message isconfigured to be delivered to an issuer of the physical account card.21. The apparatus of claim 19, further, comprising: obtaining a secureelement update request; providing a message to generate a new securecryptographic element and update the same secure cryptographic element.22. The apparatus of claim 19, wherein the message to generate a newsecure cryptographic element may be triggered periodically, and whereina period may be any of: seconds, minutes, hours, days, weeks, months,years, dynamically, on-demand, real-time.